File Name                         Description 
ntwdblib.dll                      DB-Lib interface library contains 
                                  functions for the WIN32 API 


Communication DLL                 You can use one of the following Net library:
/ Net Library One library         Dbnmpntw.dll - Named Pipes library  
for used communication protocol.  Dbmssocn.dll or dbnetlib.dll (for MSSQL 2000) 
                                  - TCP/IP Sockets library 
                                  Dbmsspxn.dll - NWLink IPX/SPX library 
                                  Dbmsrpcn.dll - Multi-Protocol library 
 

If you will use Named Pipes protocol, then it is enough to distribute the following 
files with your application: Ntwdblib.dll and Dbnmpntw.dll.
As since Named Pipes is default Net-Library for MS SQL Client, 
if Net-Library entry is not exist in registry.

When you need to use other Net Library (except Named Pipes), 
then you need to import the following data(Net Library entry) 
in the system registry for connect through TCP/IP library (for example): 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo] 
"DSQUERY"="DBMSSOCN" 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\DB-Lib] 
"AutoAnsiToOem"="on" 
"UseIntlSettings"="ON" 

File/Directory Name            Description 
\sybase\dll                    Includes API-interface and communication libraries.
Libcomn.dll                    Open Client and Open Server Common Library 
Libcs.dll                      Open Server Library 
Libct.dll                      Open Client Library 
Libintl.dll                    Locale library 
Libtcl.dll                     TLI library 
Nlmsnmp.dll                    Named Pipes Driver 
Nlwnsck.dll                    WinSock TCP/IP Driver
Nlnwlink.dll                   NWLink IPX/SPX Driver
                               You can use and deploy only one network driver.
 
\sybase\ini                    Contains initialization files 
Libtcl.cfg 
Objectid.dat 
Sql.ini 

\sybase\charsets               Contains all charsets. You can use and copy only required
                               charsets. In most cases, it is enough ôIso_1ö and ôUtf8ö 
							   charset directories. 
\sybase\locales                Contains messages for some code pages. In most cases, 
                               it is enough a ôEnglish\Iso_1ö locale directory. 

Also you need set SYBASE environment variable to a path, which contains Sybase client, 
and add drive:\sybase\dll directory to the PATH environment variable. 
You can add the following line in your autoexec.bat and change X:\ on your valid driver, 
which contains Sybase client. 

SET SYBASE=X:\sybase 
SET PATH=%PATH%;X:\sybase\dll 
Below you can see a content of Sql.ini for TCP/IP connect, where ASESRV is 
a SQL Server name, and SRVHOST(port: 5000) is a host with SQL Server.

[ASESRV]
$BASE$00=NLWNSCK,SRVHOST,5000
MASTER=$BASE$00;
$BASE$01=NLWNSCK,SRVHOST,5000
QUERY=$BASE$01;

- DB2, Informix and ODBC:
  The "Server name" field can contain DSN, which is set up in ODBC Administrator, 
  or a full datasource string with supported parameters for the required server.
  Below you can see an example of datasource string for Informix server:
  'SERVICE=ids_srv1;HOST=yourhost;PROTOCOL=OLSOCTCP;SERVER=ids_srv1;DATABASE=sysmaster;
  UID=informix;PWD=informix '.

- Interbase:
  The "Server name" field defines a remote server, path to the required database 
  and network protocol. See examples below.
  RemoteDatabase value	    Used network protocol
  :	                                TCP
  \\\                                  NetBEUI
  @	                                SPX

- Oracle:
  The property specifies a host string/service name.

- MySQL, MS SQL Server or Sybase SQL Server:
  If you connect to a remote server then "Server name" field has to include server 
  and database names divided by colon. 
  For example, "srv1:pubs" defines database name PUBS on the server SRV1.